home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
qbbs
/
cvt2qb11.zip
/
CVT2QBBS.DOC
< prev
next >
Wrap
Text File
|
1993-05-01
|
9KB
|
180 lines
██████╗ ██╗ ██╗ ████████╗ ██████╗ ██████╗ ██████╗ ██████╗ ███████╗
██╔════╝ ██║ ██║ ╚══██╔══╝ ╚════██╗ ██╔═══██╗ ██╔══██╗ ██╔══██╗ ██╔════╝
██║ ██║ ██║ ██║ █████╔╝ ██║ ██║ ██████╔╝ ██████╔╝ ███████╗
██║ ╚██╗ ██╔╝ ██║ ██╔═══╝ ██║▄▄ ██║ ██╔══██╗ ██╔══██╗ ╚════██║
╚██████╗ ╚████╔╝ ██║ ███████╗ ╚██████╔╝ ██████╔╝ ██████╔╝ ███████║
╚═════╝ ╚═══╝ ╚═╝ ╚══════╝ ╚══▀▀═╝ ╚═════╝ ╚═════╝ ╚══════╝
╒═════════════════════════════════════════════╕
│ │░░
│ T H E T A G TO Q B B S D A T A F I L E │ ░
│ │ ░
│ C O N V E R S I O N U T I L I T Y │ ░
│ │ ░
╘═════════════════════════════════════════════╛ ░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
Acknowledgements
~~~~~~~~~~~~~~~~
Thanks got to the TAG team for providing the structure information
necessary for utility authors to create the utilities that *we* all
ask for. Thanks especially to Victor Capton and Paul Williams, not only
for remaining the driving forces behind this special BBS system, but also
for giving insight into TAG's inner workings making this and other
projects soooooooo much easier to handle.
TAG is copyrighted By The T.A.G. Team
QuickBbbs (referred to as QBBS) is Copyrighted By Pegasus Software
This program is copyrighted by Rick Cooper and remains the sole
property of same. CVT2QBBS is NOT public domain, rather it's to be
considered freeware.
Guarantees/Warranties/And Other Fantasies
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
There is no warranty or guarantee offered with this program. The only
thing I will guarantee is it's ability to take up disk space.
By using this program you agree to hold harmless the author in all
regards and circumstance including but not limited to:
Damage to drives
Damage to Date
Loss of income
Increased Sexual Awareness
Change of Gender or Species
Purpose
~~~~~~~
Ain't but one purpose boys and girls and that is to allow TAG BBS
systems to interface easily and quickly with QBBS doors and utilities
that require real information rather than the make believe stuff
generated by less, application specific, more generalized Door
converters.
CVT2QBBS will create the following Files:
QUICKCFG.DAT : Main QBBS Configuration File
MSGCFG .DAT : Message Base Configuration File
FILECFG .DAT : File Base Configuration File
LIMITS .CTL : Daily Download K By S/L Restriction File
EVENTCFG.DAT : Events Configuration File
USERS .BBS : QBBS Users List Data File
ALIAS .BBS : QBBS User Handle/Alias File
FILES .BBS : QBBS File Listing Files
FB??????.BBS : QBBS CD-ROM File Listings Files.
FLSEARCH.CTL : Old Style File Search List For ALLFIX
These files are written true to QBBS Version 2.76 standards and will
interface with virtually any door or utilities designed to operate with
QBBS version 2.7? (previous QBBS version used entirely different
structures).
Command Line Switches
~~~~~~~~~~~~~~~~~~~~~
The calling syntax is as follows:
CVT2QBBS (TAG System Dir) (TAG HMS Message base) [NOFILES] [V=?]
Where :
TAG System Dir := Path to TAG node's STATUS.DAT
TAG HMS Path := Path To Hudson Message Base
NOFILES := Will Prevent CVT2QBBS from Updating List
Files
V= := Validation Key to use for new user validation
This will allow you to use QBBS call back
Verifiers (in conjunction with TAGUDATE)
for user validation
The NOFILES (case is not important) switch will prevent CVT2QBBS from
generating list files if you are running multi-node with shared file
bases. The NOFILES switch should be used at least once so your list
file system is maintained but is redundant if all file bases are
shared.
The V= parameter (which can be swapped with the NOFILES option) will
tell CVT2QBBS which validation key to use for the call back validation
portion of the configuration file. If you do not specify a validation
key the CVT2QBBS will use the first validation record. Since TAGUDATE
will adjust the user AR flags and SL (and phone number) if they are
changed in a door, you can now use a call back verifier designed for
use with QBBS. Two things to remember: The DSL will be set to the same
level as SL (they are not seperated in QBBS) and the Special flags will
be set to what ever options the user has but will NOT be changed other
wise by TAGUDATE... Again there are no SPECIAL flags with QBBS. This
means if you use the mail not validated flag with non validated users
then it will remain after validation and you *will* have to toggle it
off manually.
Setup
~~~~~
There isn't any per say. Just place CVT2QBBS in a directory that
is in your path... Make sure you CALL the program from the directory
that you wish to use as this particular QBBS node directory (the
program will write the data files to the CURRENT directory). If the
file SLK.DAT exist (by calling SETDLK before CVT2QBBS) it will use the
information within to write the LIMITS.CTL file. (See the SETDLK.DOC
file for details).
Operation
~~~~~~~~~
CVT2QBBS will maintain all of your security setups in regards to
message bases, file system, logon information, etc.. Both the security
level and FLAGS are maintained in all areas. This means that programs
that respect the QBBS security system will also respect yours without
modification. It will also maintain all of your message base setups,
Network AKAs, Origin lines, private areas, ANSI allowances and
restrictions as well. In case you are not familiar with QBBS, by the
way, USERS.BBS will be written in your HMS directory. This is means
that you will have a different USERS.BBS for each separate hudson
message base that you operate. (multiple nodes with a single HMS
base will share the USERS.BBS user list)
Used in conjunction with the rest of the utilities included in this
archive you can rest assured that interfacing to your favorite QBBS
doors and maintenance program will be smooth and efficient. Some of
the programs you will be able to run are:
Blue Wave : Proprietary Offline Mail Door
GrayQwk : The best QWK Offline Mail Door for any BBS type
AcFiles : The best file download/upload/maintenance system
About the only TAG specific setup that CVT2QBBS cannot handle is
multiple hudson message bases. If you want to use the program with
messaging system such as GrayQwk you will have to setup a directory for
each node and each message base you wish to access. This is cumbersome
but unless QBBS and it's related utility authors decided to embrace the
multiple hudson message base idea TAG will continue to be the only
system using this concept. To expand your ability to use these
utilities and programs, I would recommend using only a single message
base unless you have over 200 areas or 16mg of message base.
If you plan to run several QBBS utilities or Doors I would recommend
setting up a permanent QBBS node directory for each of your TAG node
directories and simply point each given door/utility to the proper QBBS
node directory... There is no need to maintain a separate QBBS system
for each program. This will reduce the maintenance time and disk space
usage. This would also mean you will not need other EXITINFO/QBBS data
file creation utilities (such as DoorMaster)... to create the
DorInfo?.Def, ExitInfo, and UserOn Drop files just call the
EXITINFO.EXE program and point to the correct QBBS and TAG node
directories. (See the EXITINFO.DOCs for details)
If there is a problem
~~~~~~~~~~~~~~~~~~~~~
I can be contacted via the TAGBETA, TAG, TAGDOORS echos or you can call
my BBS (Just For The Heck Of It II) at (219) 747-5971.. Or netmail me
at 1:236/16 @FidoNet
Rick Cooper